fix(v7): repair CI on every v7 pull request, and update mariadb to 3.5.4 with its IPv6 parsing change - #30668

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@prisma/client](https://www.prisma.io) ([source](https://github.com/prisma/orm/tree/HEAD/packages/client)) | imports | patch | [`7.10.0` -> `7.10.1`](https://renovatebot.com/diffs/npm/@prisma%2fclient/7.10.0/7.10.1) |

---

### Release Notes

<details>
<summary>prisma/orm (@&#8203;prisma/client)</summary>

### [`v7.10.1`](https://github.com/prisma/orm/releases/tag/7.10.1)

[Compare Source](prisma/orm@7.10.0...7.10.1)

Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.

##### Fixes

##### Prisma Client: nested `$transaction` no longer changes the options object you pass in

If you passed the same options object to a nested `tx.$transaction(...)` and later to a top-level `prisma.$transaction(...)`, the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside that old transaction:

- if the old transaction had committed, the new one failed with `P2028`;
- if the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.

```ts
const TX_OPTIONS = { timeout: 30_000, maxWait: 10_000 }

await prisma.$transaction(async (tx) => {
  await tx.$transaction(async (inner) => { /* ... */ }, TX_OPTIONS)
})

// Before 7.10.1, this call could fail with P2028 or join another transaction.
await prisma.$transaction(async (tx) => { /* ... */ }, TX_OPTIONS)
```

Prisma Client no longer modifies the options object. ([#&#8203;30368](prisma/orm#30368), thanks [@&#8203;lazerg](https://github.com/lazerg))

##### Prisma Migrate: refuse a shadow database that is the main database

Prisma Migrate now refuses to run with error `P3025` when the shadow database URL points at the same database as the main database URL. Before, `prisma migrate diff --from-migrations` with that setup dropped the real schema, rebuilt it from the migrations, and reported an empty diff. ([prisma/prisma-engines#5851](prisma/prisma-engines#5851))

##### MariaDB adapter: updated to `mariadb` 3.5.4

`@prisma/adapter-mariadb` now depends on `mariadb` 3.5.4, which fixes several security advisories in 3.5.3. The adapter no longer rewrites IPv6 hosts in connection strings, because `mariadb` 3.5.4 accepts them as written. IPv6 connection strings keep working without changes. ([#&#8203;30668](prisma/orm#30668))

##### Dependency updates

Dependencies with security advisories were updated: `mysql2`, `fast-uri`, `deepmerge-ts`, `mariadb` and `source-map-js`. ([#&#8203;30314](prisma/orm#30314), [#&#8203;30189](prisma/orm#30189), [#&#8203;30668](prisma/orm#30668))

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE2OC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Reviewed-on: https://git.oirnoir.dev/OIRNOIR/YouTube-Helper-Server/pulls/59

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@prisma/adapter-pg](https://github.com/prisma/orm) ([source](https://github.com/prisma/orm/tree/HEAD/packages/adapter-pg)) | imports | patch | [`7.10.0` -> `7.10.1`](https://renovatebot.com/diffs/npm/@prisma%2fadapter-pg/7.10.0/7.10.1) |

---

### Release Notes

<details>
<summary>prisma/orm (@&#8203;prisma/adapter-pg)</summary>

### [`v7.10.1`](https://github.com/prisma/orm/releases/tag/7.10.1)

[Compare Source](prisma/orm@7.10.0...7.10.1)

Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.

##### Fixes

##### Prisma Client: nested `$transaction` no longer changes the options object you pass in

If you passed the same options object to a nested `tx.$transaction(...)` and later to a top-level `prisma.$transaction(...)`, the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside that old transaction:

- if the old transaction had committed, the new one failed with `P2028`;
- if the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.

```ts
const TX_OPTIONS = { timeout: 30_000, maxWait: 10_000 }

await prisma.$transaction(async (tx) => {
  await tx.$transaction(async (inner) => { /* ... */ }, TX_OPTIONS)
})

// Before 7.10.1, this call could fail with P2028 or join another transaction.
await prisma.$transaction(async (tx) => { /* ... */ }, TX_OPTIONS)
```

Prisma Client no longer modifies the options object. ([#&#8203;30368](prisma/orm#30368), thanks [@&#8203;lazerg](https://github.com/lazerg))

##### Prisma Migrate: refuse a shadow database that is the main database

Prisma Migrate now refuses to run with error `P3025` when the shadow database URL points at the same database as the main database URL. Before, `prisma migrate diff --from-migrations` with that setup dropped the real schema, rebuilt it from the migrations, and reported an empty diff. ([prisma/prisma-engines#5851](prisma/prisma-engines#5851))

##### MariaDB adapter: updated to `mariadb` 3.5.4

`@prisma/adapter-mariadb` now depends on `mariadb` 3.5.4, which fixes several security advisories in 3.5.3. The adapter no longer rewrites IPv6 hosts in connection strings, because `mariadb` 3.5.4 accepts them as written. IPv6 connection strings keep working without changes. ([#&#8203;30668](prisma/orm#30668))

##### Dependency updates

Dependencies with security advisories were updated: `mysql2`, `fast-uri`, `deepmerge-ts`, `mariadb` and `source-map-js`. ([#&#8203;30314](prisma/orm#30314), [#&#8203;30189](prisma/orm#30189), [#&#8203;30668](prisma/orm#30668))

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjguMiIsInVwZGF0ZWRJblZlciI6IjQ0LjE2OC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Reviewed-on: https://git.oirnoir.dev/OIRNOIR/YouTube-Helper-Server/pulls/58